Skip to content

Remove AI releases #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
a8trejo merged 4 commits into from
Dec 16, 2024
Merged

Remove AI releases #133

a8trejo merged 4 commits into from
Dec 16, 2024

Conversation

@a8trejo
Copy link
Contributor

@a8trejo a8trejo commented Dec 16, 2024 •
edited by ellipsis-dev bot
Loading

Remove AI releases

Important

Remove AI release automation and update workflows to handle releases without AI-generated notes.

  • Workflows:
    • Deletes changeset-ai-releases.yml, removing AI-based release automation.
    • Adds changeset-release.yml to handle version bump PRs and auto-merge without AI notes.
  • Actions:
    • Updates ai-release-notes/action.yml to require git_ref, head_ref, and base_ref inputs.
  • Changelog:
    • Adds changelog-config.ts to define custom changelog functions.
  • Dependencies:
    • Adds @changesets/types to devDependencies in package.json.

This description was created by Ellipsis for 5359f82. It will automatically update as commits are pushed.

@changeset-bot
Copy link

changeset-bot bot commented Dec 16, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: 5359f82

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

ellipsis-dev[bot]
ellipsis-dev bot reviewed Dec 16, 2024
View reviewed changes
mrubens
mrubens reviewed Dec 16, 2024
View reviewed changes
mrubens
mrubens reviewed Dec 16, 2024
View reviewed changes
mrubens
mrubens reviewed Dec 16, 2024
View reviewed changes
.gitignore Outdated
roo-cline-*.vsix

# Local prompts and rules
local-prompts
Copy link
Collaborator

@mrubens mrubens Dec 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is a directory, I think a little safer to add a trailing /

@mrubens
Copy link
Collaborator

mrubens commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

@a8trejo
Copy link
Contributor Author

a8trejo commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

this will already happen, that's how changeset works by default

@a8trejo
Copy link
Contributor Author

a8trejo commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

this will already happen, that's how changeset works by default

example
https://github.com/RooVetGit/Roo-Node-Types/blob/main/CHANGELOG.md

@mrubens
Copy link
Collaborator

mrubens commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

this will already happen, that's how changeset works by default

Where is the code that prepends it to the changelog? It's built in? I noticed it was using a different format than the other entries.

@a8trejo
Copy link
Contributor Author

a8trejo commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

this will already happen, that's how changeset works by default

Where is the code that prepends it to the changelog? It's built in? I noticed it was using a different format than the other entries.

the changeset github actions takes care of that
https://github.com/changesets/action

@mrubens
Copy link
Collaborator

mrubens commented Dec 16, 2024

This can certainly be a separate thing, but can we change the code that adds to the CHANGELOG based on the changeset to use the exact same formatting as the rest of the entries in there?

this will already happen, that's how changeset works by default

Where is the code that prepends it to the changelog? It's built in? I noticed it was using a different format than the other entries.

the changeset github actions takes care of that https://github.com/changesets/action

Can we use this to make it match what's currently in the changelog? https://github.com/changesets/changesets/blob/main/docs/modifying-changelog-format.md

I don't think we need the git sha or the major/minor/match header

@a8trejo a8trejo merged commit 476e564 into main Dec 16, 2024
6 checks passed
@a8trejo a8trejo deleted the chores/remove-ai-releases branch December 16, 2024 23:20
roomote pushed a commit that referenced this pull request Jul 8, 2025
@cte
Capture more events when backfilling (#133)
3b2f9ee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ellipsis-dev ellipsis-dev[bot] ellipsis-dev[bot] left review comments

@mrubens mrubens mrubens approved these changes

@stea9499 stea9499 Awaiting requested review from stea9499

@ColemanRoo ColemanRoo Awaiting requested review from ColemanRoo

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@a8trejo @mrubens